I like the methods, but not the names; I don't think generic method names are helpful and I'd like to see more specific ones.

These are essentially "filter" methods, so maybe with should be an update to the existing filter where it accepts an array, and without should be a new reject method?

Well, given that it’s using diffKeys and intersectKeys under the hood, how about withKeys and withoutKeys? Or alternatively onlyKeys and exceptKeys?

Filter I’m guessing already exists and will take a closure. Reject is fine but I think except or without fits it better?

Edit: yep, filter takes a closure, and the issue with having it accept either a closure or with functionality, is that a filter can be both positive, negative, and based on other criteria, where with is a positive filter only. So I suggest avoiding the clash with that and with array_filter as that implies that kind of functionality from it.

Edit 2: given the intent behind your suggestion and the possibly ambiguity of using with or without at all (especially as with is sometimes a reserved operator in programming languages), I refactored to onlyKeys and exceptKeys which I think makes it clear what it does, and what you need to pass (i.e. 'keys').

Y'all are going to hate me, but I'd love to be able to pass Closures to these methods.

Y'all are going to hate me, but I'd love to be able to pass Closures to these methods.

I’d say that’s what the filter method is for. It takes a closure and performs whatever filter you want, negative, positive, or arbitrary logic.

I’d say that’s what the filter method is for. It takes a closure and performs whatever filter you want, negative, positive, or arbitrary logic.

Agree.

Naming is hard 😅 I think there should be proper symmetry:

• with and without is the simplest, though a bit implicit that it works on keys
• withKeys and withoutKeys is more explicit, but also more verbose
• includeKeys and excludeKeys — just another idea
• include and exclude — probably too generic

tbh my preference is with and without, since the parameter name will make it clear that we're talking about keys.

I think my two pennies here is that whatever first part is chosen, that Keys should still suffix, that's the convention in use elsewhere within the class for when it explicitly works with Keys instead of Values.

From a grammar perspective, the issue with "include" is it doesn't entirely communicate that it's an exclusive list, and in fairness, "with" also doesn't entirely communicate that it's an exclusive list. They both possibly imply "append" the values - whereas "only" clearly states that you're going to get "only" that back, which is the point of it.

In the context of removing certain keys and getting the remainder, "except", "exclude", "remove", "without" all work.

I did some searches and here's some more ideas that I think communicate "only" instead of "append":

• withKeys / withoutKeys, possible slightly ambiguous as above
• includeKeys / excludeKeys, possible slightly ambiguous as above
• onlyKeys / exceptKeys, not clearly antonyms for each other (Laravel uses this)
• pickKeys / dropKeys, drop is possibly ambiguous as it could imply it removes keys from the array, opposed to returning a copy, but used in JS space so has some precedence
• keepKeys / removeKeys, remove is possibly ambiguous as it could imply it removes keys from the array, opposed to returning a copy
• keepKeys / omitKeys, clearly indicates "only" on both, Go and some Python use this

Unrecommended ideas

• Filter, already exists, accepts a closure
• Pluck, already exists, accepts a single string and edits the array opposed to returning a copy
• Pop, already exists, removes the last item from the array opposed to returning a copy

I then say withKeys / withoutKeys

I then say withKeys / withoutKeys

Refactored and clean qa locally, I imagine the checks will be along in a few :)

Perfect!

Well, didn't have time to weight in again but withKeys implies to me that those keys would be added to the array, not that a copy of it with only those keys would be kept...

It's not the right name imo. It might be an unpopular opinion, but while stuff like "with" and "without" sound good in theory, they're hella confusing and I always end up having to look at what they actually do and compare it to other methods with similar generic names. I would really like it if we kept using explicit names 😔

There's also the issue of the names implying that the original array would be modified, which might not be the case depending on whether the instance is ImmutableArray or MutableArray

I’m really glad this point was raised, as I share exactly the same concerns regarding the withKeys / withoutKeys naming.

The distinction between 'adding' and 'keeping' is a crucial one. To me, withKeys naturally feels like an append operation, whereas onlyKeys or keepKeys leaves no doubt that the result is an exclusive list. I also think the point about the ...Keys suffix is spot on.

I'm afraid that with/without might be just ambiguous enough to force developers to double-check the implementation, especially when it comes to whether the original array is modified or not.

Between the explicit options, I’d personally lean towards onlyKeys / exceptKeys. Since these terms are already used in Laravel, they have the advantage of being familiar to many while remaining perfectly clear about the end result.

Well we didn't tag this yet, so no harm done. I don't really agree with you, but I also don't really care too much about it, so I'm fine changing it. Feel free to send a PR @innocenzi or @shaffe-fr or @iamdadmin with a better name. onlyKeys and exceptKeys is fine

#2097 Enzo is on it!